Remote Management of Devices

ABSTRACT

Remote configuration ensures compliance of remote devices. A server polls a device for a configuration file. The server compares the configuration file to a compliance policy. If the configuration file fails the compliance policy, the server retrieves a compliant configuration file that conforms to the compliance policy. The server sends the compliant configuration file to the device with an instruction to replace the configuration file.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 13/832,853 filed Mar. 15, 2013 and since issued as U.S. Pat. No. X,which is a continuation application of U.S. application Ser. No.12/638,171 filed Dec. 15, 2009 and since issued as U.S. Pat. No.8,423,958, which is a continuation application of U.S. application Ser.No. 11/187,224 filed Jul. 22, 2005 and since issued as U.S. Pat. No.7,657,871, with all applications incorporated herein by reference intheir entireties.

BACKGROUND OF THE DISCLOSURE

1. Field of the Disclosure

The present disclosure relates to methods and system of managingconfiguration profiles of a plurality of deployed network elements.

2. Background Art

Configuration profiles and other parameters associated with operation ofrouters and other network elements deployed in a network may be manuallybacked up using a PCMIA card or other localized medium, which typicallyrequires a technician or other experienced individual. If the routergoes down or otherwise experiences a fault condition, its return tooperation may be dependent on restoration of the configuration profilestored on the local PCMIA card.

Because the configuration profiles are stored locally, a technician mustbe dispatched to the router to instigate a manual restoration using thePCMIA card backup. The importance of these PCMIA backups is critical toinsure there is a recent restoral point for the network element. Ifthere is not a recent backup, much data can be lost.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system in accordance with one non-limiting aspectof the present disclosure;

FIG. 2 illustrates a method of managing configuration profiles of thenetwork elements in accordance with one non-limiting aspect of thepresent disclosure; and

FIG. 3 illustrates a diagrammatic representation of a machine inaccordance with one non-limiting aspect of the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present disclosure discloses an embodiment of a method for a networkhaving a network element with an original configuration profile storedtherewith which specifies operation of the network element in thenetwork. The method includes connecting a server to the network suchthat the server is remotely located from the network element and is incommunication with the network element via the network. The methodfurther includes retrieving by the server via the network the originalconfiguration profile from the network element after the network elementhas been operating in the network. The method further includes analyzingby the server the original configuration profile for compliance withdesired characteristics. The method further includes, if the originalconfiguration profile is not in compliance with the desiredcharacteristics, then manipulating by the server the originalconfiguration profile to generate a new configuration profile incompliance with the desired characteristics and forwarding by the servervia the network the new configuration profile to the network element forthe network element to store therewith in place of the originalconfiguration profile.

The present disclosure discloses an embodiment of a computer readablestorage medium containing executable code that when executed causes aserver, connected to a network having a network element with an originalconfiguration profile stored therewith which specifies operation of thenetwork element in the network, to perform steps. The steps includeretrieving the original configuration profile from the network elementafter the network element has been operating in the network. The stepsfurther include analyzing the original configuration profile forcompliance with desired characteristics. The steps further include, ifthe original configuration profile is not in compliance with the desiredcharacteristics, then manipulating the original configuration profile togenerate a new configuration profile in compliance with the desiredcharacteristics and forwarding the new configuration profile to thenetwork element for the network element to store therewith in place ofthe original configuration profile.

FIG. 1 illustrates a system 10 in accordance with one non-limitingaspect of the present disclosure. System 10 may include a number ofnetwork elements 14-24 configured to facilitate servicing electronicservices for a number of customers 30-32. Network elements 14-24 may beconfigured to interact with each other and customers 30-32. A managementserver 34 may be provided to facilitate managing operation of networkelements 14-24.

A network 36 may be provided by network elements 14-24 to facilitateelectronic data transmissions therebetween. Network 36 may be a publictelephone switching network (PSTN), advanced intelligent network (AIN),wireless intelligent networks (WIN), time division multiplex (TDM)network, packet switching or IP network, VoIP network, and the like.Network 36 may include any type of infrastructure for supporting theoperation thereof, such as terrestrial or extraterrestrial, wireless orwireline line infrastructures and/or some combination thereof. Network36 may be configured to transmit electronic data according to anyprotocol and standard, including TCP/IP, UDP, SONET, etc.

Network elements 14-24 may include any type of network elementassociated with a telecommunication, television, data, satellite, and/orcable system. For example, the network elements may be routers,gateways, hubs, central offices (COs), service switching points (SSP),soft switches, signal transfer points (STPs), service control points(SCPs), service nodes (SNs), service package applications (SPAs), mobileswitching centers (MSCs), home location registers (HLRs), visitorlocation registers (VLRs), server offices, server switches, featureservers, application program interfaces (APIs), hubs, bridges, servers,and the like.

Management server 34 may include a tool (not shown) to facilitatemanaging operation of various network elements 14-24. The tool may beconfigured to control operation of management server 34 in such a manneras to facilitate controlling operation of various network elements14-24. In accordance with one non-limiting aspect of the presentdisclosure, server 34 may be configured to communicate with networkelements 14-24 so as to facilitate managing configuration profilesassociated therewith. Management server 34 may include or be configuredto communicate with a database. The database may be configured to storeelectronic data for use by server 34 and/or network elements 14-24.

FIG. 2 illustrates a flowchart 38 of a method of managing configurationprofiles of network elements 14-24 in accordance with one non-limitingaspect of the present disclosure. The method may be executed by a toolincluded within server 34 and/or by any other suitable device includedwithin the system. The method may be embodied in a logical mediumsuitable for directing, controlling, manipulating, and performingoperations associated with the execution thereof.

Block 40 relates to retrieving configuration profiles from one or moreof network elements 14-24. The configuration profiles generally relateto electronic data associated with the operation of network elements14-24. Each network element 14-24 may include a number of differentoperation characteristics and parameters for controlling the operationthereof. This information and other information associated withdirecting and controlling operation of network elements 14-24 may beincluded with the configuration profile.

The configuration profile may be used to specify variables associatedwith the operation of network elements 14-24. As one skilled in the artwill appreciate, each network element 14-24 may have one or moredifferent parameter settings and other variables depending on theoperations associated therewith. For example, different routers in thesystem may have any number of different configuration profiles dependingon the number of customers supported, performance and quality of servicerequirements, and the like. If network elements 14-24 should experiencea fault condition or experience other interruptions in the operationthereof, the configuration profile may be used to restore the operationthereof.

The tool may control server 34 to poll network elements 14-24 for theconfiguration profiles associated therewith. For example, the tool maybe configured to periodically output instructions to network elements14-24 for requesting transport of their configuration profiles to server34 and/or the tool may issue instructions for configuring networkelements 14-24 to automatically transport their configurations profilesupon occurrence of a triggering event, such as on the first day of eachcalendar month and/or upon any changes thereto.

The configuration profiles may be retrieved after network elements 14-24are deployed in system 10. This may be advantageous for retrievingchanges in the configuration profiles made by technicians at a locallevel. For example, various network elements 14-24 may include a base orglobal configuration profile which allows it to initially operate andcommunicate when deployed in system 10. This configuration profile,however, may be adapted once deployed to support particular operationsand features. Commonly a technician or other experienced individual maybe used to adjust the parameters of the network element once deployed toconform its configuration profile to desired operation settings. Byretrieving the configuration profiles after such deployment, the presentdisclosure is able to retrieve the particular configuration file used bydeployed network elements 14-24 after it has been locally provisionedafter deployment.

Block 42 relates to storing the retrieved configuration profiles in adatabase. The database may be included on server 34 or otherwise incommunication therewith. It may be configured to support computation andother analysis of the configuration profiles. The configuration profilesmay include a network element identifier which may be used in storingthe configuration profiles on the database in a logical order. Forexample, configuration profiles associated with particular types ofnetwork elements 14-24 may be associated with each other to facilitatethe analysis thereof.

Block 44 relates to analyzing the configuration profiles for compliancewith desired management characteristics. The desired managementcharacteristics may relate to various account, inventory, traffic,historical info, and other information which may be gleaned from thestored configuration profiles. The tool may be configured toautomatically analyze the stored configuration files based on any numberof algorithms associated with desired settings and features for theconfiguration profiles.

In general, the analyzing step may be used to determine whether theconfiguration profile corresponds to required operation settings and totroubleshoot the profiles if errors are found therein. For example, eachprofile may be individually analyzed by the tool or an operator thereofto determine whether the profile is in compliance with any number ofdifferent management requirements. Non-compliant configuration profilesmay be flagged or otherwise designated, such through alerts or othermessages being sent to a network administrator.

Block 46 relates to manipulating the non-compliant configurationprofiles into compliance with the desired management characteristics.This may require manipulating one or more of the configuration profilesaccording to one or more different settings. In more detail, differentdesired management characteristics may be assigned to different networkelements. Accordingly, the configuration profiles may need to bemanipulated to correspond with the desired management characteristicsassociated with that particular type of network element 14-24.

To facilitate the manipulation process, the network element identifiersoptionally included with the retrieved configuration profiles may becross-referenced with various management characteristics. In thismanner, the tool may lookup or otherwise locate the desired operationcharacteristics for the configuration profiles of each network element.Once manipulated, the manipulated configuration profiles may be storedin place of the originally downloaded configuration files.

Block 48 relates to distributing one or more of the stored configurationprofiles to one or more of network elements 14-24. The distributedconfiguration profiles may be one of the originally downloaded profilesor a profile manipulated into compliance with the desired managementcharacteristics. The tool may be configured to distribute theconfiguration profiles to the network elements associated therewithaccording to any number of triggers.

One trigger may relate to determining a fault condition for one of thenetwork elements. The fault condition may be determined by the toolpolling the network element for its current conditions and/or by thetool receiving a message from the network element, such as through anautomatic fault reporting program included on the network element. Thetool may then locate and distribute an appropriate configuration profileto the network element experiencing the fault condition.

As described above, the tool may periodically go to router and othernetwork elements and extract all the configuration data and populate aseparate database with this information. This automated process wouldnegate the need for the manual technician process using the PCMIA card.Once this information is stored in separate data base, the presentdisclosure may be used to generate many reports based on the data thatwas taken from the router. You can generate accounting data, inventory,traffic info, historical info, and you would have a secure backup.

FIG. 3 is a diagrammatic representation of a machine in the form of acomputer system 60 within which a set of instructions, when executed,may cause the machine to perform any one or more of the methodologiesdiscussed herein. In some embodiments, the machine operates as astandalone device. In some embodiments, the machine may be connected(e.g., using a network) to other machines. In a networked deployment,the machine may operate in the capacity of a server or a client usermachine in server-client user network environment, or as a peer machinein a peer-to-peer (or distributed) network environment. The machine maycomprise a server computer, a client user computer, a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a mobile device, a palmtop computer, alaptop computer, a desktop computer, a personal digital assistant, acommunications device, a wireless telephone, a land-line telephone, acontrol system, a camera, a scanner, a facsimile machine, a printer, apager, a personal trusted device, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. It will be understood that a device of the presentdisclosure includes broadly any electronic device that provides voice,video or data communication. Further, while a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

Computer system 60 may include a processor 62 (e.g., a centralprocessing unit (CPU), a graphics processing unit (GPU), or both), amain memory 64 and a static memory 66, which communicate with each othervia a bus 68. Computer system 60 may further include a video displayunit 70 (e.g., a liquid crystal display (LCD), a flat panel, a solidstate display, or a cathode ray tube (CRT)). Computer system 60 mayinclude an input device 72 (e.g., a keyboard), a cursor control device74 (e.g., a mouse), a disk drive unit 76, a signal generation device 78(e.g., a speaker or remote control) and a network interface device 80.

Disk drive unit 76 may include a machine-readable medium 82 on which isstored one or more sets of instructions (e.g., software 84) embodyingany one or more of the methodologies or functions described herein,including those methods illustrated in herein above. Instructions 84 mayalso reside, completely or at least partially, within main memory 64,static memory 66, and/or within processor 62 during execution thereof bycomputer system 60. Main memory 64 and processor 62 also may constitutemachine-readable media. Dedicated hardware implementations including,but not limited to, application specific integrated circuits,programmable logic arrays and other hardware devices can likewise beconstructed to implement the methods described herein. Applications thatmay include the apparatus and systems of various embodiments broadlyinclude a variety of electronic and computer systems. Some embodimentsimplement functions in two or more specific interconnected hardwaremodules or devices with related control and data signals communicatedbetween and through the modules, or as portions of anapplication-specific integrated circuit. Thus, the example system isapplicable to software, firmware, and hardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein are intended for operation as software programsrunning on a computer processor. Furthermore, software implementationscan include, but not limited to, distributed processing orcomponent/object distributed processing, parallel processing, or virtualmachine processing can also be constructed to implement the methodsdescribed herein.

The present disclosure contemplates a machine readable medium containinginstructions 84, or that which receives and executes instructions 84from a propagated signal so that a device connected to a networkenvironment 86 can send or receive voice, video or data, and tocommunicate over network 86 using instructions 84. Instructions 84 mayfurther be transmitted or received over network 86 via network interfacedevice 80.

While machine-readable medium 82 is shown in an example embodiment to bea single medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more sets of instructions. The term “machine-readable medium”shall also be taken to include any medium that is capable of storing,encoding or carrying a set of instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present disclosure. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to:solid-state memories such as a memory card or other package that housesone or more read-only (non-volatile) memories, random access memories,or other re-writable (volatile) memories; magneto-optical or opticalmedium such as a disk or tape; and carrier wave signals such as a signalembodying computer instructions in a transmission medium; and/or adigital file attachment to e-mail or other self-contained informationarchive or set of archives is considered a distribution mediumequivalent to a tangible storage medium. Accordingly, the presentdisclosure is considered to include any one or more of amachine-readable medium or a distribution medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the present disclosure is not limited to such standardsand protocols. Each of the standards for Internet and other packetswitched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP)represent examples of the state of the art. Such standards areperiodically superseded by faster or more efficient equivalents havingessentially the same functions. Accordingly, replacement standards andprotocols having the same functions are considered equivalents.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. Figures are merely representational andmay not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. The present disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

1. A method, comprising: retrieving, by a server, a configuration fileassociated with a device; determining, by the server, that theconfiguration file fails a compliance policy; retrieving, by the server,a compliant configuration file that conforms to the compliance policy;and sending, by the server, the compliant configuration file to thedevice with an instruction to replace the configuration file.
 2. Themethod of claim 1, further comprising periodically receiving theconfiguration file sent from the device.
 3. The method of claim 1,further comprising determining a local provision of the configurationfile after deployment of the device.
 4. The method of claim 1, furthercomprising receiving the configuration file after deployment of thedevice.
 5. The method of claim 1, further comprising determining a typeof the device from the configuration file.
 6. The method of claim 5,further comprising retrieving a parameter associated with the type ofthe device.
 7. The method of claim 6, further comprising comparing theconfiguration file to the parameter associated with the type of thedevice.
 8. A system, comprising: a processor; and a memory storing codethat when executed causes the processor to perform operations, theoperations comprising: retrieving a configuration file locally stored bya device; determining a local provision of the configuration file afterdeployment of the device; determining the configuration file fails acompliance policy; retrieving a compliant configuration file thatconforms to the compliance policy; and sending the compliantconfiguration file to the device with an instruction to replace theconfiguration file locally stored by the device.
 9. The system of claim8, wherein the operations further comprise generating the compliantconfiguration file.
 10. The system of claim 8, wherein the operationsfurther comprise periodically receiving the configuration file sent fromthe device.
 11. The system of claim 8, wherein the operations furthercomprise periodically receiving the configuration file according to acalendar.
 12. The system of claim 8, wherein the operations furthercomprise determining a type of the device from the configuration file.13. The system of claim 12, wherein the operations further compriseretrieving a parameter associated with the type of the device.
 14. Thesystem of claim 13, wherein the operations further comprise comparingthe configuration file to the parameter associated with the type of thedevice.
 15. A memory storing instructions that when executed cause aprocessor to perform operations, the operations comprising: retrieving aconfiguration file locally stored by a device; determining a localprovision of the configuration file after deployment of the device;determining the configuration file fails a compliance policy; retrievinga compliant configuration file that conforms to the compliance policy;and sending the compliant configuration file to the device with aninstruction to replace the configuration file locally stored by thedevice.
 16. The memory of claim 15, wherein the operations furthercomprise generating the compliant configuration file.
 17. The memory ofclaim 15, wherein the operations further comprise periodically receivingthe configuration file sent from the device.
 18. The memory of claim 15,wherein the operations further comprise periodically receiving theconfiguration file according to a calendar.
 19. The memory of claim 15,wherein the operations further comprise determining a type of the devicefrom the configuration file.
 20. The memory of claim 19, wherein theoperations further comprise: retrieving a parameter associated with thetype of the device; and comparing the configuration file to theparameter associated with the type of the device.